Add CLI lifecycle integration tests with vitest #50

Copilot · 2026-02-09T06:31:03Z

End-to-end tests for the complete user workflow: objectdocs init → content creation → objectdocs build → objectdocs migrate.

Tests (`packages/cli/test/cli-lifecycle.test.mjs`)

6 sequential tests in a shared temp directory mirroring real usage:

CLI help — binary loads, all commands listed
objectdocs init — .fumadocs/ scaffolded, content/package.json with scripts, .gitignore updated, deps installed
Idempotent init — second run detects existing installation
Content creation — MDX files, meta.json, docs.site.json written and validated
objectdocs build — Next.js production build produces .next output
objectdocs migrate — .md → .mdx with frontmatter extraction, H1 removal, body preservation, meta.json update

Bug fix (`packages/site/next.config.mjs`)

The init workflow was broken: Turbopack (Next.js 16) cannot resolve imports outside the project root. Content lives at ../../docs/ relative to .fumadocs/.source/, which is outside .fumadocs/.

outputFileTracingRoot: path.resolve(__dirname, '../..'),

This extends Turbopack's resolution scope to include the content directory. Monorepo build is unaffected.

Infrastructure

Added vitest to packages/cli devDependencies
vitest.config.mjs with 600s timeout for integration tests
Updated test script from echo "No test" → vitest run

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

vercel · 2026-02-09T06:31:09Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectdocs	Ready	Preview, Comment	Feb 9, 2026 7:08am

- Add vitest as dev dependency to packages/cli - Create comprehensive integration test verifying full CLI lifecycle: init → content creation → build - Fix outputFileTracingRoot in next.config.mjs to allow Turbopack to resolve content files outside the .fumadocs project root - Update packages/cli test script from placeholder to vitest run Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

github-actions · 2026-02-09T06:45:31Z

🚀 Preview Deployment

This pull request will be automatically deployed to Vercel.

Preview Links

📝 Documentation: Will be available once Vercel deployment completes
🌍 Languages: English (/en/docs) and Chinese (/cn/docs)

Build Status

Check the CI workflow for build status and any errors.

Automated preview information for PR #50

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

github-actions · 2026-02-09T06:56:53Z

🚀 Preview Deployment

This pull request will be automatically deployed to Vercel.

Preview Links

📝 Documentation: Will be available once Vercel deployment completes
🌍 Languages: English (/en/docs) and Chinese (/cn/docs)

Build Status

Check the CI workflow for build status and any errors.

Automated preview information for PR #50

Copilot

Pull request overview

Adds end-to-end CLI lifecycle integration coverage (init → content → build → migrate) using Vitest, and updates the site’s Next.js config to fix Turbopack file tracing for content outside the project root.

Changes:

Add Vitest-based CLI lifecycle integration test suite covering init/build/migrate.
Add Vitest configuration + wire up pnpm test for packages/cli.
Update packages/site/next.config.mjs with outputFileTracingRoot to fix init/build workflows under Next.js/Turbopack.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
pnpm-lock.yaml	Adds vitest (and transitive toolchain) to the workspace lockfile.
packages/site/next.config.mjs	Sets `outputFileTracingRoot` for broader file tracing scope.
packages/cli/vitest.config.mjs	Adds long timeouts suitable for end-to-end integration tests.
packages/cli/test/cli-lifecycle.test.mjs	New sequential lifecycle integration tests executing real CLI commands.
packages/cli/package.json	Switches `test` to `vitest run` and adds `vitest` devDependency.

Files not reviewed (1)

pnpm-lock.yaml: Language not supported

Copilot · 2026-02-09T07:33:02Z

packages/cli/test/cli-lifecycle.test.mjs

+const __dirname = path.dirname(__filename);
+
+const CLI_PATH = path.resolve(__dirname, '../bin/cli.mjs');
+const MONOREPO_ROOT = path.resolve(__dirname, '../../..');


MONOREPO_ROOT is declared but never used. Please remove it to avoid confusion about whether the tests depend on monorepo paths.

Suggested change

const MONOREPO_ROOT = path.resolve(__dirname, '../../..');

Copilot · 2026-02-09T07:33:02Z

packages/cli/test/cli-lifecycle.test.mjs

+function runCli(args, options = {}) {
+  const { cwd = testDir, env: extraEnv = {}, timeout = 300_000 } = options;
+  return execFileSync(process.execPath, [CLI_PATH, ...args], {
+    cwd,
+    timeout,


runCli defaults to a 5-minute execFileSync timeout, but the vitest config allows 10 minutes. Long npm install / next build runs could be killed by the shorter process timeout even though the test timeout hasn’t elapsed. Consider bumping the default to match the vitest timeout (or threading it through from config).

Copilot · 2026-02-09T07:33:02Z

packages/cli/test/cli-lifecycle.test.mjs

+  });
+}
+
+describe('CLI Lifecycle: init → content → build', () => {


These tests rely on shared state across multiple it(...) blocks. To prevent future flakiness if vitest is configured to run tests concurrently, make the suite explicitly sequential (e.g., describe.sequential(...) or equivalent vitest sequencing config).

Suggested change

describe('CLI Lifecycle: init → content → build', () => {

describe.sequential('CLI Lifecycle: init → content → build', () => {

Copilot · 2026-02-09T07:33:03Z

packages/cli/package.json

+  "devDependencies": {
+    "vitest": "^4.0.18"
  }


Adding vitest (which requires Node >=20 per the lockfile) changes the effective Node baseline for this workspace/package, but package.json doesn’t declare an engines.node range. Consider adding engines (and aligning CI/release, which currently uses Node 18) or pinning to a Vitest version compatible with the supported Node version.

Copilot · 2026-02-09T07:33:03Z

pnpm-lock.yaml

+  vite@7.3.1:
+    resolution: {integrity: sha512-w+N7Hifpc3gRjZ63vYBXA56dvvRlNWRczTdmCBBa+CotUzAPf5b7YMdMR/8CQoeYE5LX3W4wj6RYTgonm1b9DA==}
+    engines: {node: ^20.19.0 || >=22.12.0}
+    hasBin: true


vite@7.3.1 declares a strict Node engine requirement (^20.19.0 || >=22.12.0). Since this is now in the lockfile, installs on Node 18 will fail and even “Node 20” environments must be new enough. Align supported Node versions/CI (or pin to a toolchain that supports the intended Node baseline).

Copilot · 2026-02-09T07:33:03Z

pnpm-lock.yaml

+  vitest@4.0.18:
+    resolution: {integrity: sha512-hOQuK7h0FGKgBAas7v0mSAsnvrIgAvWmRFjmzpJ7SwFHH3g1k2u37JtYwOwmEKhK6ZO3v9ggDBBm0La1LCK4uQ==}
+    engines: {node: ^20.0.0 || ^22.0.0 || >=24.0.0}
+    hasBin: true


vitest@4.0.18 requires Node ^20.0.0 || ^22.0.0 || >=24.0.0. Please ensure the repo’s documented/CI Node version matches this (the release workflow currently uses Node 18), or pin Vitest to a version that supports the older runtime.

Copilot · 2026-02-09T07:33:03Z

packages/cli/test/cli-lifecycle.test.mjs

+ */
+
+import { describe, it, expect, beforeAll, afterAll } from 'vitest';
+import { execSync, execFileSync } from 'child_process';


execSync is imported but never used in this test file. Removing unused imports keeps the integration test easier to maintain and avoids lint/tooling warnings if added later.

Suggested change

import { execSync, execFileSync } from 'child_process';

import { execFileSync } from 'child_process';

Initial plan

5864794

Copilot AI assigned Copilot and hotlong Feb 9, 2026

Copilot started work on behalf of hotlong February 9, 2026 06:31 View session

vercel bot deployed to Preview February 9, 2026 06:32 View deployment

Copilot AI and others added 2 commits February 9, 2026 06:44

feat: add migrate command test to CLI lifecycle suite

11cd9cb

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

github-actions bot added the dependencies label Feb 9, 2026

test: verify content body preservation in migrate test

7811b07

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Add tests for CLI command project initialization~~ Add CLI lifecycle integration tests with vitest Feb 9, 2026

Copilot AI requested a review from hotlong February 9, 2026 06:50

Copilot finished work on behalf of hotlong February 9, 2026 06:50

vercel bot deployed to Preview February 9, 2026 07:08 View deployment

hotlong marked this pull request as ready for review February 9, 2026 07:27

Copilot AI review requested due to automatic review settings February 9, 2026 07:27

Copilot started reviewing on behalf of hotlong February 9, 2026 07:27 View session

hotlong merged commit 357a2f9 into main Feb 9, 2026
11 checks passed

Copilot AI reviewed Feb 9, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add CLI lifecycle integration tests with vitest #50

Add CLI lifecycle integration tests with vitest #50

Copilot AI commented Feb 9, 2026 •

edited

Loading

Uh oh!

vercel bot commented Feb 9, 2026 •

edited

Loading

Uh oh!

github-actions bot commented Feb 9, 2026

Uh oh!

github-actions bot commented Feb 9, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 9, 2026

Uh oh!

Copilot AI Feb 9, 2026

Uh oh!

Copilot AI Feb 9, 2026

Uh oh!

Copilot AI Feb 9, 2026

Uh oh!

Copilot AI Feb 9, 2026

Uh oh!

Copilot AI Feb 9, 2026

Uh oh!

Copilot AI Feb 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	describe('CLI Lifecycle: init → content → build', () => {
	describe.sequential('CLI Lifecycle: init → content → build', () => {

	import { execSync, execFileSync } from 'child_process';
	import { execFileSync } from 'child_process';

Add CLI lifecycle integration tests with vitest #50

Add CLI lifecycle integration tests with vitest #50

Conversation

Copilot AI commented Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Tests (packages/cli/test/cli-lifecycle.test.mjs)

Bug fix (packages/site/next.config.mjs)

Infrastructure

Uh oh!

vercel bot commented Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 9, 2026

🚀 Preview Deployment

Preview Links

Build Status

Uh oh!

github-actions bot commented Feb 9, 2026

🚀 Preview Deployment

Preview Links

Build Status

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented Feb 9, 2026 •

edited

Loading

Tests (`packages/cli/test/cli-lifecycle.test.mjs`)

Bug fix (`packages/site/next.config.mjs`)

vercel bot commented Feb 9, 2026 •

edited

Loading